Skip to content

Support out-of-app config directory.#697

Closed
kyrofa wants to merge 1 commit into
nextcloud:masterfrom
kyrofa:feature/support_config_outside_app
Closed

Support out-of-app config directory.#697
kyrofa wants to merge 1 commit into
nextcloud:masterfrom
kyrofa:feature/support_config_outside_app

Conversation

@kyrofa

@kyrofa kyrofa commented Aug 1, 2016

Copy link
Copy Markdown
Member

As requested by @oparoz and @jospoortvliet:

The Nextcloud pi drive device is based upon snappy ubuntu core. Snaps are squashfs images which by definition are read-only. This makes the Nextcloud config read-only as well, which greatly limits its usefulness. This PR introduces support for hosting the config out of the main application (in the case of the snap, in a writable area so the rest of the application can remain read-only). It does this by using the environment variable $NEXTCLOUD_CONFIG_DIR. If it's set, it is used as the config directory. If not set, it uses the default <root>/config/.

Note that this is fairly well-tested, but I can't pretend to have hit every code path that uses the config. There may be a better place to put this code. If so, please let me know.

The Nextcloud pi drive device is based upon snappy ubuntu core. Snaps
are squashfs images which by definition are read-only. This makes the
Nextcloud config read-only as well, which greatly limits its usefulness.
This commit introduces support for hosting the config out of the main
application (in the case of the snap, in a writable area so the rest of
the application can remain read-only). It does this by using the
environment variable `$NEXTCLOUD_CONFIG_DIR `. If it's set, it is used
as the config directory. If not set, it uses the default
`<root>/config/`.

Signed-off-by: Kyle Fazzari <kyle@canonical.com>
@mention-bot

Copy link
Copy Markdown

@kyrofa, thanks for your PR! By analyzing the annotation information on this pull request, we identified @DeepDiver1975, @icewind1991 and @LukasReschke to be potential reviewers

@MorrisJobke

Copy link
Copy Markdown
Member

I think this is a duplicate of #660 and I like the other one more. Maybe the setup controller thing is missing over there.

@MorrisJobke

Copy link
Copy Markdown
Member

@kyrofa Are you okay with closing this in favor of the other PR?

@kyrofa

kyrofa commented Aug 1, 2016

Copy link
Copy Markdown
Member Author

@MorrisJobke oh! You're completely right, I'm sorry! I'll go ahead and close this, though note that the snap makes use of the SetupController.php change (it looks like the other PR author knows about this and is working on it).

@kyrofa kyrofa closed this Aug 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants